LSPx 2026 Release Notes

This page provides details about features, enhancements, and bug fixes for the latest versions of the LSPx application.
See below for what's new in PowerHub v1.0.56.
For last year's release notes see LSPx 2025 Release Notes
See also the LSPx user guides

Wednesday, September 02, 2026

Enhancements, Features and Bug Fixes | v1.0.56

Features and Enhancements

Area	Description
DACs: Support equipment	The new section on the DAC form covering Support equipment has been enabled. Overview This change introduces a comprehensive update to the DAC form, specifically targeting the identification and scoping of support equipment. This update incorporates new questions designed to facilitate accurate trade and vendor resourcing by capturing granular details for equipment not installed by the main tool OEM. Primary Support Equipment Identification A new conditional section has been added to the DAC form, below the "Additional Scope Comments" field. Users are presented with a primary identification question: • Question: "Does the tool have support equipment not installed by the main tool OEM?". This question is optional; it does not have to be answered. • Purpose: To identify additional equipment to ensure accurate and complete scoping as well as facilitate trade and/or vendor resourcing. • Functionality: This is a radio-button selection (Yes/No). Selecting "Yes" expands the form to display subsequent scoping questions, while selecting "No" leaves the extra questions hidden. Categorized Support Equipment Scoping When you select “Yes”, the form displays a series of categorized dropdown questions • Default State: All dropdowns default to "N/A" to minimize manual entry for non-applicable categories. • Conditional Expansion: Selecting any value other than "N/A" triggers the appearance of specific child questions to capture detailed scoping information. Detailed Scoping and Part Number Tracking For each identified piece of support equipment, users are required to provide specific lifecycle and identification data: • Lifecycle Status: A radio-button selection to define the equipment's status. o Install/CIP DACs: Options include "New Buy", "Reuse", "CIP", and "No Scope". o Demo DACs: Options include "Scrap", "Prep for Reuse", and "Keep in Place". • Identification Details: A text field for providing the "Vendor Part Number" or "NIT number" (specifically required for reuse equipment). Additional Support Equipment Comments The last question provides an optional rich text input field titled "Additional Support Equipment not Covered Above." This allows Tool Owners and Area Coordinators to provide supplementary technical details or specific scoping instructions that are not captured by the structured dropdowns. Form Validation Logic The "Send to AE" action now includes enhanced validation protocols for the support equipment section: • Mandatory Fields: If a support equipment category is selected (other than N/A), the corresponding Lifecycle Status and Vendor Part Number questions become mandatory. Scope and Applicability • Applicable Sites: These enhancements are active for TD and HVM sites.• Applicable DAC Types: The new questions appear on Install, CIP, and Demo DAC forms. • Exclusions: These changes do not apply to RP sites. Reports • For those who generate reports on DACs, there are new database views. Please contact LSPx support to get details on the new views
DAC: Rich text fields	The rich text fields on the DAC and other forms have been made resizable so as the user can stretch it to see all the contents.

Bug Fixes

Area	Description
Approving revisions: System slowness	After a user approved an IFC Main Pack revision, the system could become slow for all users for about 1 minute. This has been fixed.
DACs: Closed DACs	Sometimes when a user was reviewing a closed DAC and they navigated away from the page, the system would prompt them to save changes even though you can not edit closed DACs. This has been fixed.
Copy Popouts: LC1	The copy popout functionality was not working for LC1 in Qiryat Gat, this had been fixed.
Leadsheets: Updated By	On the Leadsheets grid, the “Updated By” and “Updated On” columns were not always accurate. This has been fixed.

Thursday, August 13, 2026

Enhancements, Features and Bug Fixes | v1.0.55

Features and Enhancements

Area	Description
Autodesk: SFV2 API failure	Users can now generate draft PDFs and issue revisions even when Autodesk fails to convert a drawing to the SFV2 viewer format. Previously, if the AutoCAD viewer translation failed, LSPx blocked the entire revision/draft workflow, this restriction has been removed. What's changed: • Revisions and drafts proceed as normal when drawings have been successfully uploaded and converted to PDF, even if the SFV2 viewer translation fails. • A new info icon appears in the Action column for drawings where the preview is unavailable. Hovering over it displays: "Preview not available. Use the 'Generate draft PDF' feature." • The eye icon (with tooltip "View preview") continues to display for drawings where the full viewer is available. • Drawings that fail to upload or convert to PDF still show the red triangle warning, and issuing a revision or generating a draft that includes those drawings will display an error message prompting the user to check drawing status. Impact: AE users are no longer blocked from continuing the tool design process when the Autodesk viewer is unavailable, reducing delays and eliminating a recurring workflow bottleneck caused by Autodesk
BIM File Processing Alert	A new automated monitoring job has been added to detect when BIM file processing in BIM360/ACC slows down or fails. The job runs every 15 minutes and checks the average file processing time over the past hour. If the average exceeds 60 seconds, an email alert is automatically sent to the Basesite support team with diagnostic SQL queries for immediate investigation. This improvement ensures faster detection and response to file upload processing delays, reducing the risk of prolonged outages going unnoticed.
Leadsheets: page labels	Generated PDFs now use the title of the drawing on a page as the page label instead of using the pack name on every page.
DCRs: Old records are now closed	DCRs approved on or before June 26th 2026 have all been set to closed. AEs should close any DCR approved from June 27th onwards.

Bug Fixes

Area	Description
ECNs: Sites Impacted	When editing an ECN form, if there were more than 4 sites impacted, the user could not see the full list of sites. Now, when the user hovers over the “+” indicator, the full list will be displayed.
---	---
---	---

Wednesday, August 05, 2026

Enhancements, Features and Bug Fixes | v1.0.54

Features and Enhancements

Area	Description
Leadsheets: PDFs on template tools	Uploading files to template/subpack tools was previously restricted to DWG file types. Users can now also upload PDFs to template/subpack tools.
Leadsheets: Replacing DWGs with PDFs	Previously there was a restriction preventing users from uploading a file with the same name as a file that was previously uploaded if the extension was not also the same. Now users can upload a DWG and then upload a PDF with the same name. Users do not need to delete the previous file before uploading the new one.

Bug Fixes

Area	Description
DACs: PDF Export	When a user has 2 DACs open on different browser tabs and they exported one to PDF, the date from the incorrect DAC sometimes appeared in the PDF printout. This has been fixed.
DCRs: Resolved date	When DCRs were closed and the grid of DCRs refreshed, the “Resolved Date” column was not populated in the gris for those closed DCRs. This has been fixed.

Monday, July 27, 2026

Enhancements, Features and Bug Fixes | v1.0.53

Features and Enhancements

Area	Description
DCR Workflow: AC & PM Review Steps Merged	The DCR workflow has been simplified by combining the previously separate Area Coordinator (AC) and TI PM review steps into a single "AC/PM Review" step. What's changed: • TI PMs can now create DCRs: The "DCR" option is now available in the Create menu for users with the TI PM role, matching the existing AC privilege. • Single review step: The separate "AC Review" button has been removed. A single "AC/PM Review" button now handles the review, and upon submission the DCR moves directly to "DCR Approval" status. • Renamed fields: The "Approved By:" field on the DCR form has been renamed to "Reviewed By AC/PM:" to accurately reflect the action. A new "Approved By:" field now appears below it to capture the final approver. • Historical records updated: Any DCRs previously in "PM Reviewed" status have been migrated to "DCR Approval". DCRs that were only "AC Reviewed" retain that status and still require a PM review for hours and cost entry. • Review audit trail preserved: The "Reviewed By AC/PM:" field displays the historical review type and reviewer name. See the DCR User Guide for full details
DCR Workflow: New "Close" Transition for AE Design Leads & Managers	AE Design Leads and AE Design Managers can now formally close an approved DCR, providing a clear end-to-end lifecycle for the DCR process. What's changed: • New "Close" button: Users with the "AE Design Lead" or "AE Design Manager" role will see a "Close" button when viewing a DCR in "Approved" status. This button is not visible to other roles. • New "Closed" status: Clicking "Close" transitions the DCR to a new dedicated "Closed" status, distinct from any pre-existing statuses. The status is reflected on both the DCR form and the grid column. • New "Closed By:" field: A new field appears on the DCR form beneath "Approved By:", displaying who closed the DCR • New "Closed" date/time field: A "Closed" date/time field appears on the form between "Resolved" and "Design Start", showing when the DCR was closed. This field displays "N/A" for DCRs not in "Closed" status • Closure email notification: When a DCR is closed, an email is sent to all stakeholders mirroring the approval email • Restricted actions on closed DCRs: Once a DCR is "Closed", no action buttons are available on the form except "Reopen", which remains available to Design Managers only. • Full audit trail**: The DCR history and transitions log the closure event with the closer's details and timestamp. See the DCR User Guide for full details
ECN: Export to Excel	Users can now export the ECN (Engineering Change Notice) grid to an Excel spreadsheet. • A new "Export to Excel" button is available on the ECN Log page, positioned to the right of the "Add ECN" button. • Clicking the button generates an .xlsx file named using the format: [SiteName] ECN Export YYYY-MM-DD.xlsx. • If filters are applied to the ECN grid, only the filtered rows are exported.

Bug Fixes

Area	Description
Tool Install Grid: Shows no data	Sometimes when a user returns to the LSPx tab in the browser where the Tool Install Schedule is open and they add a filter to the grid, the page would display “No Data to display” and the user would have to refresh the page and try again. This has been fixed.
Leadsheets: Extra pages	In rare circumstances, a draft PDF would incorrectly have extra pages which were duplicates of other pages. This has been fixed.
Tool details: Error message	Occasionally, when a user viewed the tool details page, a message reading "Permission status for MOK tool is not loaded" would be displayed. This has been fixed.

Monday, July 13, 2026

Enhancements, Features and Bug Fixes | v1.0.52

Features and Enhancements

Area	Description
Leadsheets: ACC Support	LSPx has been enhanced to support Autodesk Construction Cloud in parallel with BIM360. Projects can now be added to ACC and configured to work in LSPx. Basesite will do this in cooperation with your local Intel Doc Control team. Users of Leadsheets and revision functionality will see no functional changes and existing BIM360 functionality remains intact.
Leadsheets: ACC Migration	LSPx has been enhanced to support migration of projects from BIM360 to Autodesk Construction Cloud. We will work with the Doc Control team to manage the migration of projects, one functional area at a time.

Thursday, July 02, 2026

Enhancements, Features and Bug Fixes | v1.0.51

Features and Enhancements

Area	Description
DAC: Formatting on Form	There have been some minor UI changes to the indentation of questions on the DAC form to conform with the new supplier equipment questions, see next item.
DAC: Supplier Equipment	NOTE: This functionality is disabled until the Design Managers request it to be turned on. At the end of the DAC form there is a new optional question (currently hidden): “Does the tool have support equipment not installed by the main tool OEM?”. Answering “Yes” to this question will display a further 10 questions which each have further sub questions depending on how the parent question is answered. If you do not answer “Yes” to the main supplier equipment question the sub questions will remain hidden and you can process the DAC form as before. For those who generate reports on DACs, there are new database views. Please contact LSPx support to get details on the new views.

Bug Fixes

Area	Description
Returning users	Previous users whose LSPx account was deactivated were receiving an error when trying to self-register. This has been fixed.
RP Schedule	The functionality to convert decoders to reference packs was broken, this has been fixed.

Wednesday, June 17, 2026

Enhancements, Features and Bug Fixes | v1.0.50

Features and Enhancements

Area	Description
Tools: Auto adding ACs and TI PMs	The system adds Area Coordinators and Tool Install PMs as stakeholders on tools from the schedule once a day. Previously if one of these changed on the schedule, the new person was added to the tool whilst leaving the first person as an AC or PM stakeholder on the tool. A change has been made so that if an AC or TI PM on a tool was added by the system but is no longer the name in the schedule, that person will be removed as a stakeholder from the tool. ACs and TI PMs who were added as stakeholders by users will not be removed. Note that the names of ACs and TI PMs in the schedule are in plain text and that those plain text names sometimes do not match the name of any user or sometimes there is more than one user who matches. In either of those cases a stakeholder is not added.
Readiness Tracker: Funding column	The “Funding” column in the Tool Install Schedule (home page) has been removed on the Ocotillo site at the request of the Design Manager.

Bug Fixes

Area	Description
POC Data: FIOP assignments	The assignment data for some FIOP POCs was not being pulled from FaSTr, this has been fixed.

Wednesday, June 10, 2026

Enhancements, Features and Bug Fixes | v1.0.49

Features and Enhancements

Area	Description
RODs: ACs TI PMs and TOs	The ROD form has 3 new stakeholder sections under “People” listing the area coordinators, tool install project managers and tool owners associated with the tool the ROD is raised on. When any action on a ROD causes an email to be sent, those new stakeholder groups will be copied on the emails.
Design readiness filters	On the Tool Install Schedule (home page) of LSPx the following columns have had their filters modified to allow users to select from the list of possible options instead of typing values into the filter • DAC Status • Funding • Layout • POC

Thursday, June 04, 2026

Enhancements, Features and Bug Fixes | v1.0.48

Features and Enhancements

Area

Description

Pedestal IFC Revisions: Folder structure

The IFC approval workflow has been removed for Pedestal Packs to streamline the folder structure in BIM360/ACC. When a Pedestal Pack revision is issued at the IFC milestone, numbered revision folders are now created directly under "024 - IFC" instead of inside an "Awaiting Review" subfolder. The "Awaiting Review" and "Approved" subfolders are no longer generated. The approve (✅) and reject (❌) action icons are no longer displayed for Pedestal IFC revisions — both for newly issued and previously issued revisions. Main Pack IFC revisions continue to follow the existing approval workflow and folder structure with no changes.

Wednesday, May 20, 2026

Enhancements, Features and Bug Fixes | v1.0.47

Features and Enhancements

Area	Description
DMR Approvals: Notified users	When a DMR is approved, all Tool Owners and Tool Install PMs on that tool will now also get the approval email. The full list of recipients of DMR emails notifications is documented at the end of the DMR Change Requests user guide Users can unsubscribe from DMR emails and other emails. See the section on Managing Site Subscriptions at the end of the User Profile Management page for details. If you are the assignee of a specific DMR, you will be notified about that change request even if you have unsubscribed.
Revisions: Attachment limit	When issuing a revision of a tool or subpack, the attachment limit has been increased from 5 files to 10 files.
Interface Plates: 5 letter CEID	Previously, when the system auto populated the interface plate field on DACs, it was using the first 3 letters of the CEID to match. This has now been updated to use all 5 letters of the CEID to match the interface plate to the tool
Download all attachments	Where attachments are added to a form, there is a new download icon above the attachment grid with the tooltip “Download all as a zip file”. This will allow the user to download all the attached files together.
DACs: RP/Goby CEID File Name	The field “RP/Goby CEID File Name” has been removed from the DAC form.

Bug Fixes

Area	Description
DACs: Interface Plates	When the system auto populated the interface plate field on DACs, sometimes a random IP for a different CEID was being added. This has been corrected.
DACs: comments	The “Additional Scope Comments” field was editable after a DAC was closed. This has been fixed and the field is no longer editable on closed DACs
Forms: Simultaneous edits	When 2 users had the same ROD, DAC or SDD form opened and both edited it, the edits saved by the first user were lost. An update has been made so as the second user will be prompted to refresh the page if the form was edited since they opened the page in the app.
Power POCs: Actual Length	Sometimes, when a user added an actual length to a Power POC, the change history was not recorded and those changes do not appear in the change history dialog. The change history is properly recorded now but the change history of some previous actual lemngths will not be available.

Wednesday, April 22, 2026

Enhancements, Features and Bug Fixes | v1.0.46

Bug Fixes

Area	Description
Mapping dialog filtering	Users could not filter using the “Tool” column in the leadsheet mapping dialog. This has been fixed.
Adding stakeholders	Sometimes users could not add stakeholders to certain tools due the Project field not being set from the schedule, this has been fixed.
FaSTr data on mechanical tab	When a user updated the data of mechanical POCs in FaSTr and then went to review the data in LSPx, the updates were not being pulled in straight away. This has been fixed. Note that if a change is made in FaSTr and a Design Lead issues a revision before anyone reviews the Mechanical POCs in LSPx, then the changes will not appear in the PIP spreadsheet. You need to open the Mechanical POC tab on a tool to get recent changes
Date filters	On some of the grids in LSPx when a user filtered a date field to Today, the system sometimes did not filter to Today but selected a different date. This has been fixed.

Wednesday, April 08, 2026

Enhancements, Features and Bug Fixes | v1.0.45

Features and Enhancements

Area	Description
Design Readiness Tracker	The Funding column on the Tool Install Schedule on the Chandler was not showing the correct values. This was due to an incorrect value on the Chandler DCN project which meant that the related records need to be updated. This is now complete and the Funding column shows the correct data.
Leadsheets: Tools with same files	Previously a drawing could only be uploaded for a single life of a tool. An enhancement now allows uploading files with the same name to multiple lives of the tool.
Leadsheets: 4 new columns	There are 4 new columns on the leadsheet page to give more information on file details. Extension: The filetype extension that was uploaded Source: Can have one of four values • “System” for subpack folders • “RP” for files which were mapped from the scraped RP file list • “SubPack Upload” for files which were uploaded to template tools by users • “LSP Upload” for files which were uploaded to LSP tools by users Updated By: The user who mapped, copied, uploaded or restored a file or the user who created a folder by creating a template tool or by adding a subpack to an LSP tool. Updated On: the date and time the subpack folder or the file was last modified
Leadsheets: BIM360 access error	Sometimes users log into BIM360 in the browser with their company email and then go to upload files in LSPx which needs their Intel email. The error message has been modified to state which email address is failing so as the user will know to log out of their BIM360 own company account.
Leadsheets: Blank subpack on LSP	An issue occurred where a subpack was added to an LSP tool and the eye icon was not displayed. This occurred as one user added the subpack to a tool immediately after another user issued the subpack on the template tool. A check has been put in place to ensure the subpack revision is fully processed before another user can add it to a tool.
Leadsheets: Error message for bad files	When generating a draft or issuing a revision the error message displayed when hovering over the red triangle in the revision grid or the draft menu will now details the files that are causing the issue.
Framework Updates	The Angular and .NET frameworks upon which LSPx is built have been upgraded. Users may notice small changes to the user interface. If you notice something that does not look correct or something that is not functioning as it should please log a ticket using the “Support” button.
Security Updates	Issues flagged by Intel code security scans were addressed. These do not have any effect on functionality.

Bug Fixes

Area	Description
Leadsheets: Duplicate files in Add dialog	When adding files from RPs or other tools, some files were listed twice, this has been fixed. Note that there are a few cases where files were incorrectly deleted from BIM360 after a revision was published and then readded, these will still be listed twice in the dialog.
Leadsheets: File sorting	On the leadsheet, sometimes the file sort order was incorrect after using autosort when the file names had suffixes after the number. This has been fixed.
LSS Requests: Pasting	Some users were intermittently unable to paste LSPx Tray nodes into the grid in the LSS Request page. This has been fixed

Thursday, March 12, 2026

Enhancements, Features and Bug Fixes | v1.0.44

Features and Enhancements

Area	Description
Uploading files: transport errors	When users upload leadsheet files there can occasionally be transient network issues such as connection reset, DNS resolution failure, TCP timeout, or TLS handshake failure. LSPx has been enhanced to retry the upload for transport failures up to 3 times with exponential backoff (500ms, 2s, 4.5s) before presenting an error to the user.
Leadsheets: Drafts issue	When issuing revisions and generating drafts, users could be prevented from generating drafts. This was being caused by one user adding a revision and another generating drafts on the same tool in a short timeframe. The behaviour has been enhanced to prevent users generating a draft whilst a revision is still being processed. The “Generate Draft PDF” menu will be replaced with a greyed-out menu reading “Generating Revision Pack...” or “Generating Draft PDF...” whilst one of those processes is still pending.

Bug Fixes

Area	Description
Leadsheets: Duplicate files in add dialog	When mapping leadsheet files, the grid of files in the mapping window would show some duplicate records, this has been fixed. Note that there are a few cases where files were incorrectly deleted from BIM360 after a revision was published and then readded, these will still be listed twice in the dialog.
Leadsheets: Drawing already mapped	When mapping leadsheet files, users could get a false error saying that the files were already mapped. This was being caused by two users adding a revision and mapping files on the same tool in a short timeframe. This has been fixed.
Popouts: Sort order	The default sorting on the Popout tab grid has been mofified to be more user friendly, it is now Popout Name, then POC Ref
RODs API: date filter	The RODs API used by reporting personell was not filtering by created date correctly. This has been fixed.
Schedule	The job which populates AC & PM on tools from the Schedule was failing. This has been fixed.
Workers API Sync	The job which deactivated LSPx Intel users when the left Intel was failing. This has been fixed.
Interface Plates: Archive folders	The job that scrapes interface plate files was not returning file names from some archive folders. This has been fixed.

Thursday, February 12, 2026

Enhancements, Features and Bug Fixes | v1.0.43

Features and Enhancements

Area	Description
Global search: Performance	The performance of the global search has been improved, especially when searching for template/subpack tools.
Power POCs: Edit cable details	Users with the role “AE Electrical Engineer” are now able to edit the cable override size and verified voltage drop values on power POCs.

Bug Fixes

Area	Description
Leadsheets: Uploading files	When users were uploading files from a local drive and they dragged the files from Windows Explorer, then sometimes the file would be listed 2 or 4 times in the dialog. This has been fixed so as each file is uploaded only once when dragging and dropping.
POCs: HPM tab	On some tools, the comment field on HPM POCs was displaying text when it should have been blank, this has been fixed.
PIP file: HPM worksheet	When exporting a PIP file on some sites, the borders on the HPM worksheet in the Excel file were not correct. This has been fixed.
Popouts: Adding a popout	When popout admins tried to add a Popout, it was not adding, this has been fixed.
DAC report view	A view used by reporting personell was returning the incorrect closed date for old DACs which were migtated from JIRA to LSPx. That has been fixed.

Thursday, January 22, 2026

Enhancements, Features and Bug Fixes | v1.0.42

Features and Enhancements

Area	Description
PIP file: Pedestal packs	When a user adds a revision for a Pedestal Pack on a tool in LSPx, the PIP Excel file will no longer be downloaded to the user’s machine, nor will it be uploaded to BIM360
DACs:	When a user navigated away from a tool's DAC Details page without making any changes, the system was displaying a confirmation popup which read “Your Draft is not Saved”. This message will no longer appear when the user has made no changes
DACs: Industrial Engineers	Industrial Engineers now have read only access to DACs
ECNs: Global search	When you use the global tool search at the top of the LSPx app, the results now include ECN records for the searched tools.

Bug Fixes

Area	Description
RODs: Dates	When an existing ROD was updated, the Due Date sometimes displayed an incorrect year if the date was for late December. This has been fixed.
PIP file: VPMS	The VPMS worksheet on exported PIP files was not formatted correctly, this has been fixed.
PIP file: Revision	The revision on the bottom of the POC worksheets was incorrectly showing the first revision instead of the latest, this has been fixed
DCR: Root Cause	The cause "Supplier Data Updater" has been corrected to be "Supplier Data Update"
Leadsheet: Add	When adding subpacks, some of the latest revisions did not display when the “Latest RP Revision” toggle was switched on and would only appear when it was switched off. This has been fixed.
DACs: Return date	In Ocotillo, when the duration between the tool’s Pedestal Design Start and the tool Design Start was less than 25 days the DAC return due date was calculated incorrectly. This has been fixed.